👋 Welcome back goetz! A progress list of the required criteria for merging this PR into master will be added to the body of your pull request. There are additional pull request commands available for use with this pull request.

@GoeLin This change now passes all automated pre-integration checks.

ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details.

After integration, the commit message for the final commit will be:

8343875: Minor improvements of jpackage test library

Reviewed-by: mbaesken

You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed.

At the time when this comment was updated there had been 15 new commits pushed to the master branch:

• a64ed9d: 8305186: Reference.waitForReferenceProcessing should be more accessible to tests
• 0f26915: 8334771: [TESTBUG] Run TestDockerMemoryMetrics.java with -Xcomp fails exitValue = 137
• 0b3561a: 8355387: [jittester] Disable downcasts by default
• ... and 12 more: https://git.openjdk.org/jdk17u-dev/compare/207dd0f5b8b9bf52e22dd3e597a60af19975fe1f...master

As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details.

➡️ To integrate this PR with the above commit message to the master branch, type /integrate in a new comment.

This backport pull request has now been updated with issue from the original commit.

Webrevs

• 01: Full - Incremental (dfb8afd5)
• 00: Full (dfb8afd5)

The parent pull request that this pull request depends on has now been integrated and the target branch of this pull request has been updated. This means that changes from the dependent pull request can start to show up as belonging to this pull request, which may be confusing for reviewers. To remedy this situation, simply merge the latest changes from the new target branch into this pull request by running commands similar to these in the local repository for your personal fork:

git checkout goetz_backport_8343875
git fetch https://git.openjdk.org/jdk17u-dev.git master
git merge FETCH_HEAD
# if there are conflicts, follow the instructions given by git merge
git commit -m "Merge master"
git push

I read nothing about omitted DirectoryContentVerifierTest .java .
Seems it is not in 17 ?
Otherwise looks okay.

Hi @MBaesken
That test was already omitted in the backport to 21, see openjdk/jdk21u-dev#2315
Thanks for the review!

⚠️ @GoeLin This change is now ready for you to apply for maintainer approval. This can be done directly in each associated issue or by using the /approval command.

/integrate

Going to push as commit 45bbc37.
Since your change was applied there have been 22 commits pushed to the master branch:

• f7bad98: 8327180: Failed: java/io/ObjectStreamClass/ObjectStreamClassCaching.java#G1
• b93970b: 8308780: Fix the Java Integer types on Windows
• 9d3acf8: 8302838: jabswitch main() should avoid calling exit explicitly
• ... and 19 more: https://git.openjdk.org/jdk17u-dev/compare/207dd0f5b8b9bf52e22dd3e597a60af19975fe1f...master

Your commit was automatically rebased without conflicts.

@GoeLin Pushed as commit 45bbc37.

💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored.